The cargo update brought in wirm 2.2.0 in Cargo.lock, but Cargo.toml
still specified 2.1.0. This caused Bazel to use the old version while
our code was fixed for the new API. Update Cargo.toml to match.

Per discussion, we don't want to update wirm at this time. This commit:
- Reverts Cargo.toml wirm version back to 2.1.0
- Reverts all wirm API changes (Instructions::new and Module::parse)
- Downgrades Cargo.lock to wirm 2.1.0

Files reverted:
- rs/embedders/src/wasm_utils/instrumentation.rs (3 changes)
- rs/embedders/src/wasm_utils/system_api_replacements.rs
- rs/embedders/src/wasm_utils/validation.rs
- rs/embedders/benches/embedders_bench/src/lib.rs
- rs/embedders/tests/instrumentation.rs (6 changes)
- rs/embedders/tests/misc_tests.rs (2 changes)
- rs/embedders/tests/spec_tests.rs
- rs/embedders/tests/wirm_round_trip.rs

Update rust.MODULE.bazel to match the dependency versions in Cargo.toml:
- ic-agent: ^0.40.1 → ^0.45.0
- ic-utils: ^0.40.1 → ^0.45.0
- ic-identity-hsm: ^0.40.1 → ^0.45.0
- ic-transport-types: ^0.40.1 → ^0.45.0
- dfx-core: ^0.1.4 → ^0.3.0
- ic-bn-lib: 0.1.7 → 0.1.14
- ic-gateway: rev → tag v0.4.0
- ic-http-gateway: rev c17ad1b... → rev 895d573...
- proptest: ^1.5.0 → =1.6.0

This ensures Bazel uses the same dependency versions as Cargo.

Regenerated Cargo.Bazel.json.lock and Cargo.Bazel.toml.lock to reflect
the updated dependency versions in rust.MODULE.bazel.

…ng/new-update

Updated Cargo.toml and rust.MODULE.bazel to use tag=v0.4.2 instead of
rev to match Cargo.lock. This eliminates the duplicate ic-http-gateway
entry that was causing the GitHub dependency submission job to fail.

Updated fqdn from 0.3.11 to 0.5.2 in pocket_ic_server to resolve
version conflict with ic-bn-lib 0.1.14, which requires fqdn 0.5.x.
This ensures all fqdn dependencies use version 0.5 or higher.

It's annoying for external contributors that CI is automatically kicked
off on pushes to master on the forked repos and then fail. This adds
another condition to prevent them from being triggered.

---------

Co-authored-by: Bas van Dijk <bas@dfinity.org>

…8790)

This makes it much easier to locate code that mutates a `CanisterState`
(simply grep for the 4 methods that return a `CanisterState` or a
mutable reference to one). Which comes in very handy when
`CanisterStates` are wrapped in `Arcs`, as mutating (too many of) said
`Arcs` may turn out to be very expensive.

…veFromUnvalidated` for some BlockProposal validation failures (#8809)

This will make it consistent with the other types of artifacts. See:
1.
https://github.com/dfinity/ic/blob/8910873dccbe92b31127d6350cdb90d6bbd50f52/rs/consensus/src/consensus/validator.rs#L911-L915
2.
https://github.com/dfinity/ic/blob/8910873dccbe92b31127d6350cdb90d6bbd50f52/rs/consensus/src/consensus/validator.rs#L1477-L1478
3.
https://github.com/dfinity/ic/blob/8910873dccbe92b31127d6350cdb90d6bbd50f52/rs/consensus/src/consensus/validator.rs#L1760-L1762

- Updated ic-bn-lib-common version spec in bazel/rust.MODULE.bazel from 0.1 to 0.1.4
- Regenerated Bazel lock files to resolve fqdn version conflicts
- Updated test data file with latest Cargo.Bazel.toml.lock snapshot
- This ensures all fqdn dependencies use version 0.5.x as required by ic-bn-lib 0.1.14